SGI Freeware 1999 August

home *** CD-ROM | disk | FTP | other *** search

/ SGI Freeware 1999 August / SGI Freeware 1999 August.iso / dist / fw_geomview.idb / usr / freeware / info / geomview-5.z / geomview-5

Wrap

Text File | 1999-01-26 | 41.6 KB | 1,032 lines

Info file: geomview, -*-Text-*- produced by texinfo-format-buffer from file: geomview.tex File: geomview Node: Non-Euclidean Geometry, Prev: Gcl Reference, Up: Top, Next: Mathematica Non-Euclidean Geometry ********************** Geomview supports hyperbolic and spherical geometry as well as Euclidean geometry. The three buttons at the bottom of the *Main* panel are for setting the current geometry type. In each of the three geometries, three models are supported: *Virtual*, *Projective*, and *Conformal*. You can change the current model with the *Model* browser on the *Camera* panel. Each Geomview camera has its own model setting. The default model is all three spaces is *Virtual*. This corresponds to the camera being in the same space as, and moving under the same set of transformations as, the geometry itself. In Euclidean space *Virtual* is the most useful model. The other models were implemented for hyperbolic and spherical spaces and just happen to work in Eucldiean space as well: *Projective* is the same as *Virtual* but by default displays the unit sphere, and *Conformal* displays everything inverted in the unit sphere. In hyperbolic space, the *Projective* model setting gives a view of the projective ball model of hyperbolic 3-space imbedded in Euclidean space. The camera is initially outside the unit ball. In this model, the camera moves by Euclidean motions and geometry moves by hyperbolic motions. *Conformal* model is similar but shows the conformal ball model instead. In spherical space, the *Projective* model gives a view of half of the 3-sphere imbedded in Euclidean 3-space. Spherical motions give rise to projective transformations in the *Projective* model, and to Moebius transformations in the *Conformal* model. In both of these models the camera moves by Euclidean motions. In *Projective* and *Conformal* models, the unit sphere is drawn by default. You can turn it off and on at will using the *Draw Sphere* button in the *Camera* panel. In the *Conformal* model, polygons and edges are subdivided as necessary to make them look curved. The parameters which determine this subdivision can be set with the `set-conformal-refine' gcl command. There are several sample hyperbolic space objects in the `data/geom/hyperbolic' subdirectory of the Geomview directory (`/u/gcg/ngrap/data/geom/hyperbolic' on the Geometry Center's system). Likewise, the subdirectory `data/geom/spherical' contains several sample spherical space objects. File: geomview Node: Mathematica, Prev: Non-Euclidean Geometry, Up: Top, Next: OOGL.m Mathematica Graphics in Geomview or RenderMan ********************************************* Geomview comes with some Mathematica packages that let you use use Geomview to display Mathematica graphics. Mathematica is a commercial mathematical software system available from Wolfram Research, Inc. There are two ways to do this. 1. Use Mathematica to write a graphics object to a file in OOGL format or in RIB format. 2. Use Geomview as the default display for all 3D graphics output in Mathematica. You can also use these packages to save Mathematica graphics in RenderMan (RIB) format. Since the format of Mathematica graphics objects is different from the OOGL formats, both of these methods involve translating Mathematica graphics to OOGL format. Geomview is distributed with a Mathematica package which does this translation. Before doing either of the above you must install this package. * Menu: * OOGL.m:: Generating OOGL files in Mathematica. * Geomview.m:: Geomview as Mathematica's Default 3D Display. * RenderMan:: Generating RenderMan files in Mathematica. * Remote Display:: Using Geomview and Mathematica on different computers. * Package Details:: Some details about the packages. * Package Installation:: Installing the Mathematica->Geomview package. File: geomview Node: OOGL.m, Prev: Mathematica, Up: Mathematica, Next: Geomview.m Using Mathematica to generate OOGL files ======================================== The package `OOGL.m' allows Mathematica to write graphics objects in OOGL format. To use it, give the command `<< OOGL.m' to Mathematica to load the package. The `WriteOOGL[FILE,GRAPHICS]' command writes an OOGL description of the 3D graphics object GRAPHICS to the file named FILE. This package also provides the `Geomview' command which sends a 3D graphics object to Geomview. The first time you use this command it starts up a copy of Geomview. Later calls send the graphics to the same Geomview. There are two ways to use the `Geomview' command. `Geomview[GRAPHICS]' Sends the 3D graphics object GRAPHICS to Geomview as a geom named `Mathematica'. Subsequent usage of `Geomview[GRAPHICS]' replaces the `Mathematica' object in Geomview with the new GRAPHICS. ``Geomview[NAME,GRAPHICS]'' Sends the 3D graphics object GRAPHICS to Geomview as a geom named NAME. You can use multiple calls of this form with different names to cause Geomview to display several Mathematica objects at once and allow independent control over them. % math Mathematica 2.0 for SGI Iris Copyright 1988-91 Wolfram Research, Inc. -- GL graphics initialized -- In[1] := <<OOGL.m In[2] := Plot3D[Sin[x + Sin[y]], {x,-2,2},{y,-2,2}] Out[2] := -Graphics3D- This displays graphics in the usual Mathematica way here. In[3] := WriteOOGL["math.oogl", %2] Out[3] := -Graphics3D- This displays nothing new but writes the file `math.oogl'. You can now load that file into Geomview on any computer. Alternately, you can use the `Geomview' command to start up a copy of Geomview from within Mathematica. In[5] := Geomview[%2] Out[5] := -Graphics3D- File: geomview Node: Geomview.m, Prev: OOGL.m, Up: Mathematica, Next: RenderMan Using Geomview as Mathematica's Default 3D Display ================================================== The package `Geomview.m' arranges for Geomview to be the default display program for 3D graphics in Mathematica. To load it, give the command `<< Geomview.m' to Mathematica. Thereafter, whenever you display 3D graphics with `Plot3D' or `Show', Mathematica will send the graphics to Geomview. Loading `Geomview.m' implicitly loads `OOGL.m' as well, so you can use the `Geomview' and `WriteOOGL' as described above after loading `Geomview.m'. You do not have to separately load `OOGL.m'. % math Mathematica 2.0 for SGI Iris Copyright 1988-91 Wolfram Research, Inc. -- GL graphics initialized -- In[1] := <<Geomview.m In[2] := Plot3D[x^2 + y^2, {x, -2, 2}, {y, -2, 2}] Out[2] := -SurfaceGraphics- This invokes geomivew and loads the graphics object into it. In[3] := Plot3D[{x*y + 6, RGBColor[0,x,y]}, {x,0,1}, {y,0,1}] Out[3] := -SurfaceGraphics- This replaces the previous Geomview object by the new object. In[4] := Geomview[{%2,%3}] Out[4] := {-SurfaceGraphics-, -SurfaceGraphics-} This displays both objects at once. You also can have more than one Mathematica object at a time on display in Geomview, and have separate control over them, by using the `Geomview' command with a name, *Note OOGL.m::. In[5] := Graphics3D[ {RGBColor[1,0,0], Line[{ {2,2,2},{1,1,1} }] }] Out[5] := -Graphics3D- In[6] := Geomview["myline", %5] This addes the `Line' specified in `In[5]' to the existing Geomview display. It can be controlled independently of the "Mathematica" object, which is currently the list of two plots. In[7] := <<GL.m If you're on an SGI, loading `GL.m' returns Mathematica to its usual 3D graphics display. To do this on a NeXT you should load `PSDirect.m' if you are using Mathematica in a notebook, or `NeXT.m' if you invoked Mathematica from a shell. The following plot will appear in a normal static Mathematica window. In[8] := ParametricPlot3D[{Sin[x],Sin[y],Sin[x]*Cos[y]}, {x,0,Pi},{y,0,Pi}] Out[8] := -Graphics3D- We can return to Geomview graphics at any time by reloading `Geomview.m'. In[9] := <<Geomview.m In[10] := Show[%8] Out[10] := -Graphics3D- In[11] := ParametricPlot3D[ {(2*(Cos[u] + u*Sin[u])*Sin[v])/(1 + u^2*Sin[v]^2), (2*(Sin[u] - u*Cos[u])*Sin[v])/(1 + u^2*Sin[v]^2), Log[Tan[v/2]] + (2*Cos[v])/(1 + u^2*Sin[v]^2)}, {u,-4,4},{v,.01,Pi-.01}] Out[11] := -Graphics3D- This last plot is Kuen's surface, a surface of constant negative curvature. Parametrization from Alfred Gray's *Modern Differential Geometry of Curves and Surfaces* textbook. File: geomview Node: RenderMan, Prev: Geomview.m, Up: Mathematica, Next: Remote Display Using Mathematica to generate RenderMan files ============================================= In addition to the `WriteOOGL' and `Geomview' commands described above, the package `OOGL.m' also defines the command `WriteRIB' which writes a 3D graphics object to a RenderMan RIB file: `WriteRIB[FILE, GRAPHICS]' writes GRAPHICS to file FILE. RenderMan is a commercial rendering system available from Pixar, Inc., which can produce extremely high quality images. In[1] := <<OOGL.m In[2] := <<Graphics/Polyhedra.m In[3] := Graphics3D[Cube[]] Out[3] := -Graphics3D- In[4] := WriteRIB["cube.rib", %3] Out[4] := -Graphics3D- This generates the file `math.rib'. This is a ready-to-render RIB file of the given geometry, using a default camera position, lighting, and the "plastic" shader. In a shell window, type `render cube.rib' to generate the image file `mma.tiff'. Of course, you need to have RenderMan installed for this to work. A shortcut to render from inside Mathematica is `WriteRIB["!render", foo]'. `WriteRIB' works by first converting the Mathematica graphics object to OOGL format using `WriteOOGL' and then calls an external program `oogl2rib' to convert OOGL to RIB format. The oogl2rib program takes several options which you can specify in a string as an optional third argument to `WriteRIB'. The default option string is `" -n mma.tiff "', which indicates that the RIB file should generate a rendered TIFF file named `mma.tiff'. A particularly useful option is `-g', which tells oogl2rib to convert only the geometry into a RIB fragment. You can insert that fragment into a full RIB file of your own making with camera positions and shaders of your choice, to harness the full power of RenderMan. The full usage of oogl2rib is: oogl2rib [-n NAME] [-B R,G,B] [-w WIDTH] [-h HEIGHT] [-fgb] [INFILE] [OUTFILE] By default it reads from stdin and writes to stdout. Either INFILE or OUTFILE may be `-', which means use stdin/stdout. The options are: `-n NAME' Use NAME for the name of the rendered TIFF file (default "geom.tiff") or framebuffer window (default "geom.rib"). `-B R,G,B' Use background color (R,G,B). Each component ranges from 0 to 1. Default: none. `-w WIDTH -h HEIGHT' Rendered frame will be WIDTH by HEIGHT pixels. `-f' RIB file renders to on-screen framebuffer instead of TIFF file. `-g' Output only the geometry in RIB format. `-b' Output only a Quick Renderman clip object. Ignores -nBwhf. File: geomview Node: Remote Display, Prev: RenderMan, Up: Mathematica, Next: Networked Geomview Using Geomview and Mathematica on Different Computers ===================================================== It is possible to use Geomview to display graphics generated by Mathematica running on a different computer. If each computer is either an SGI or a NeXT and they are networked together, you can tell Mathematica to use a remote host for Geomview graphics. If you want to use Mathematica on a computer that is not networked with your Geomview computer, or on any kind of computer other than an SGI or a NeXT (for example a PC or a Mac), you can write out *chunk* files in Mathematica which you transfer to the Geomview computer and then translate to OOGL format. * Menu: * Networked Geomview:: Using a networked Geomview host. * Chunks:: Transporting Mathematica files to Geomview by Hand. File: geomview Node: Networked Geomview, Prev: Remote Display, Up: Remote Display, Next: Chunks Using a Networked Geomview Host ------------------------------- The `Geomview' command looks at the `DISPLAY' or `REMOTEHOST' environment variables to try to determine if you are logged in from another computer. If either of these indicates that you are, `Geomview' will attempt to run Geomview on that computer. In order for this to work, your network must be configured such that the Mathematica computer can successfully `rsh' to the Geomview computer without giving a password. You can also explicitly set the `DisplayHost' option to the `Geomview' command to a string which is the desired hostname, for example: In[1] := << OOGL.m In[2] := Plot3D[Sin[x + Sin[y]], {x,-2,2},{y,-2,2}] Out[2] := -Graphics3D- In[3] := Geomview[%3, DisplayHost->"riemann"] This displays the graphics `%3' on the remote host named `riemann'. `Geomview' recognizes the string `"local"' as a value for `$DisplayHost'; it forces the graphics to be displayed on the local machine. In addition to knowing the name of the machine you want to run Geomview on, the `Geomview' needs to know the type of that machine (SGI or NeXT). By default, `Geomview' assumes that it is the same kind of computer as the one you are running Mathematica on. The `MachType' option lets you explicitly specify the type of the `DisplayHost' computer; it should be one of the strings `"sgi"' or `"next"'. You can use `SetOptions' to change the default `DisplayHost' and `MachType'. For example, In[4] := SetOptions[Geomview, DisplayHost->"riemann", MachType->"sgi"] arranges for `Geomview' to run Geomview on an SGI workstation named `riemann'. File: geomview Node: Chunks, Prev: Networked Geomview, Up: Remote Display, Next: Package Details Transporting Mathematica Files to Geomview by Hand -------------------------------------------------- The auxilliary function `WriteChunk' is for those who can only use Mathematica on a non-Unix machine (Mac, PC) or a Unix machine that is not on a network with an SGI or NeXT. `WriteChunk[FILE, GRAPHICS]' generates a file named FILE which contains the graphics object GRAPHICS in the format accepted by `math2oogl'. You can transfer that file to a computer that has Geomview installed on it and then use the programs `math2oogl', `oogl2rib', and `geomview' directly from the shell. These programs are distributed in the `bin/sgi' (on SGIs) or `bin/next' (on NeXTs) subdirectory of the Geomview directory, and may have been installed so that they are on your `path'. In[1]:= <<OOGL.m In[2]:= Plot3D[ Sin[x + Sin[y]], {x,-2,2}, {y,-2,2} ] Out[2]= -SurfaceGraphics- In[3]:= WriteChunk["mychunk",%2] This writes the file `mychunk' which contains a description of the graphics object. You can then transfer this file to an SGI or NeXT and type math2oogl < mychunk > mma.oogl to convert it to the OOGL file `mma.oogl' which you can then view using Geomview. This is the equivalent of the `WriteOOGL' command. For a result equivalent to the `Geomview' or `Show' commands, type math2oogl -togeomview Mathematica geomview < mychunk The `WriteRIB' command can be emulated from the shell as math2oogl < mychunk | oogl2rib -n mma.tiff File: geomview Node: Package Details, Prev: Chunks, Up: Mathematica, Next: Package Installation Details of the Mathematica->Geomview Package ============================================ The `OOGL.m' package uses the external program `math2oogl' to convert `Graphics3D' objects to OOGL format, because a compiled external program is able to do this conversion many times faster than Mathematica. The converter will sometimes handle colored SurfaceGraphics objects correctly that Mathematica does not handle correctly, which means that Geomview[object] sometimes works where Show[object] will give errors. The converter supports the `Polygon', `Line', and `Point' graphics primitives, `RGBColor Graphics3D' directives, and `SurfaceGraphics' objects with or without `RGBColor' directives, and lists of any combination of these. It silently ignores all other directives. The Mathematica to RenderMan conversion is actually a two-step process: Mathematica->OOGL (math2oogl), and OOGL->RenderMan (oogl2rib). The math2oogl program has only been tested on SGIs and NeXTs, but could theoretically compile on any machine. The oogl2rib program depends on the OOGL (Object Oriented Graphics Language) libraries, which now only exist on SGI and NeXT machines. In the `WriteOOGL' and `WriteRIB' commands, filename can either be a string containing a filename, an `OutputStream' object, or a string starting with a `!' to send the output to a command. Object can be a `Graphics3D' object, a `SurfaceGraphics' object, or a list of these. The packages work best with Mathematica 2.0 or better. With version 1.2, the Geomview display is always on the local host. File: geomview Node: Package Installation, Prev: Package Details, Up: Mathematica, Next: Installation Installing the Mathematica Packages =================================== If Geomview is properly installed on your system according to the instructions in *Note Installation::, then the Mathematica-to-Geomview packages should work as described here; there should be no need for additional installation procedures. In practice, however, it is sometimes necessary to taylor the installation of the Mathematica packages and/or of Geomview itself to suit the needs of a particular system. This section contains details about how the installation works; if the Mathematica-to-Geomview connection does not seem to work for you after following the Geomview installation procedure, consult this section to see what might need to be fixed. In this section, the phrase *Geomview installation* refers any of the procedures in *Note Installation::. The way the Mathematica packages work and are installed is the same regardless of whether you have one of the binary distributions or the source distribution. 1. The relevant mathematica files are `OOGL.m', `Geomview.m', and `BezierPlot.m'; Mathematica must be able to find these files. They are distributed in the `$GEOMROOT/mathematica' subdirectory of the binary distributions, and in the `$GEOMROOT/src/bin/geomutil/math2oogl' subdirectory of the source distribution. These files need to be in a directory that is on Mathematica's search path. You can look at the value of the `$Path' variable in a Mathematica session on your system to see a list of the directories on Mathematica's search path. The Geomview installation procedure puts copies of the Mathematica packages into a directory that you specify (`MMAPACKAGEDIR'). This should ensure that Mathematica can find them. Alternately, you could arrange to append the pathname of the Mathmematica package subdirectory of the Geomview distribution to the `$Path' variable each time you run Mathematica. 2. The package `OOGL.m' needs to be able to invoke the programs `geomview', `math2oogl', and `oogl2rib'. The Geomview installation procedure installs these programs into a directory that you specify for executables (`BINDIR'). Ideally, this directory should be on your shell's `$path'. More specifically, it should be on the `$path' of the shell in which Mathematica runs; the directory `/usr/local/bin' is usually a good choice. You can see the list of directories on this path by giving the command `!echo $path' in Mathematica. If for some reason you can't arrange for `geomview', `math2oogl', and `oogl2rib' to be in a directory on the shell's `$path', you can modify `OOGL.m' to cause it to look for them using absolute pathnames. To do this, change the definitions of the variables `$GeomviewPath' and `$GeomRoot', which are defined near the top of the file. Change `$GeomviewPath' to the absolute pathname of the `geomview' shell script on your system. Change `$GeomRoot' to the absolute pathname of the `$GEOMROOT' directory on your system. If you do this, you should also make sure there are copies of `geomview', `math2oogl', and `oogl2rib' in the `$GEOMROOT/bin/sgi' (on an SGI) or `$GEOMROOT/bin/next' (on a NeXT) directory. 3. The `geomview' shell script, which `OOGL.m' uses to invoke Geomview, needs to be able to find the geomview executable file (which is called `gvx' on the SGI and `Geomview.app/Geomview' on the NeXT). The Geomview installation procedure should have been taken care of this, but if your Mathematica session doesn't seem to be able to invoke Geomview, it's worth double-checking that the settings in the `geomview' script are correct. File: geomview Node: Installation, Prev: Package Installation, Up: Top, Next: SGI Binary Installation Installation ************ What you do to install Geomview depends on which kind of computer you have (SGI or NeXT) and on whether you have the source distribution or the binary distribution. In general, if you don't care about looking at Geomview's source code, you should get the binary distribution. Its installation is much easier and quicker than that for the source code. * Menu: * SGI Binary Installation:: Installing the SGI Binary Distribution. * NeXT Binary Installation:: Installing the NeXT Binary Distribution. * Source Code Installation:: Compiling and Installing the Source Code Distribution. * Obtaining:: Obtaining Geomview. File: geomview Node: SGI Binary Installation, Prev: Installation, Up: Installation, Next: SGI Binary Detail Installing the SGI Binary Distribution ====================================== If you have just obtained a copy of the SGI binary distribution (file `geomview-sgi.tar.Z'), you should be able to run Geomview and make use of most of its features immediately after unpacking it by `cd''ing to the directory that it is in and typing `geomview'. In order to fully install Geomview so that you can run it from any directory and use all of its features, follow the steps in this section. In particular, you must go through this installation procedure in order to use Geomview to display Mathematica graphics. Geomview is distributed in a directory that contains various files and subdirectories that Geomview needs at run-time, such as data files and external modules. It also contains other things distributed with Geomview, such as documentation and (in the soure-code distribution) source-code. We refer to the root directory of this tree as the `$GEOMROOT' directory. This is the directory called `Geomview' that is created when you unpack the distribution file. To install Geomview on your system, arrange for the `$GEOMROOT' directory to be in a permanent place. Then, in a shell window, `cd' to that directory and type `install'. This runs a shell script which does the installation after asking you several questions about where you want to install the various components of Geomview. After running the `install' script you should now be able to run Geomview from any directory on your system. (You may need to give the `rehash' command in any shells on your computer that were started up before you did the installation.) The `install' script puts copies of the files in `$GEOMROOT/bin/sgi' and `$GEOMROOT/man' into the directories you specified for executables and man pages, respectively. Once you have done the installation you can cut down one the disk space required by Geomview by removing some files from these directories, since copies have been installed elsewhere. You should first test that your installed Geomview works properly because once you remove these files from their distribution directories you will not be able to do the installation again. In particular, the files you can remove are `$GEOMROOT/bin/sgi': Remove all files from here except `gvx', which is the geomview executable file. DO NOT REMOVE `gvx'. It is not installed elsewhere. `$GEOMROOT/man': You can remove all the files in this directory. File: geomview Node: SGI Binary Detail, Prev: SGI Binary Installation, Up: SGI Binary Installation, Next: NeXT Binary Installation Details of the SGI Binary Installation -------------------------------------- The `install' script should be self-explanatory; just run it and answer the questions. This section gives some details for system administrators and other users who may want to know more about the installation. The installation is actually done by `make'; the `install' script queries the user for the settings of the following `make' variables and then invokes `make install'. `GEOMROOT': the absolute pathname of the Geomview root directory. The `geomview' shell script, which is what users invoke to run Geomview, uses this to set various environment variables that Geomview needs. It is very important that this be an *absolute* pathname --- i.e. it should start with a '/'. `BINDIR': a directory where executable files are installed. The `geomview' shell script goes here, as well as various other auxiliary programs that can be used in conjunction with `geomview'. This should be a directory that is on users' `$path'. These auxiliary programs are distributed in the `$GEOMROOT/bin/sgi' directory; if you specify this directory for `BINDIR', they are left in that directory. `MANDIR': a directory where Unix manual pages are installed. These are distributed in the `$GEOMROOT/man' subdirectory; if you specify this directory for `MANDIR', they are left in that directory. `MMAPACKAGEDIR': a directory where Mathematica packages are installed. This should be a directory that Mathematica searches for packages that it loads; you can see what directories your Mathematica searches by looking at the value of the `$Path' variable in a Mathematica session. The installation process will install some packages there which allow you to use Geomview to display Mathematica graphics. These packages are distributed in the `$GEOMROOT/mathematica' subdirectory; if you specify this directory for `MMAPACKAGEDIR', or if you specify the empty string for `MMAPACKAGEDIR', the packages are left in that directory. For more details about the way these Mathematica packages connect to Geomview, *Note Package Installation::. File: geomview Node: NeXT Binary Installation, Prev: SGI Binary Detail, Up: Installation, Next: NeXTStep Binary Detail Installing the NeXT Binary Distribution ======================================= 1. If you have just obtained a copy of the NeXTStep binary distribution (file `geomview-next.tar'), you can unpack it by double-clicking on it in the Workspace. This will open up a File Viewer panel showing, among other things, a NeXT Installer package called `Geomview.pkg'. 2. The first thing you should do is double-click on `Geomview.pkg' to invoke the NeXT Installer. You will be asked where you want to install it; typically it should go in `/LocalApps' or in `~/Apps' in your home directory. You should now be able to run Geomview and make use of most of its features by double-clicking on the installed `Geomview.app' icon. 3. There are some aspects of the installation, however, that the NeXT Installer can't handle. In order to fully install Geomview so that you can use all of its features, you should run the `install' script in the `Geomview.app' directory. In particular, you must go through this installation procedure in order to use Geomview to display Mathematica graphics. To run the `install' script you can open `Geomview.app' in the Workspace by selecting it and picking `File->Open as Folder' from the Workspace menu. This will pop up a File Viewer panel showing the contents of `Geomview.app'. Scroll down to the file named `install', and double-click on it. This will open a terminal window and run the script in that window. Alternately, you can open a terminal window yourself, cd to `Geomview.app', and run `install' there. The `install' script does the installation after asking you several questions about where you want to install the various components of Geomview. After running the `install' script, Geomview is completely installed. If in the future you move `Geomview.app' to some other location you should run `install' again. 4. This step is optional. Geomview's example data files are in the `Geomview.app/data' directory. If you are on a network with both SGI workstations and NeXTStep workstations, and you want to install Geomview to run on both, you can save disk space by having the two installations share a common data directory. To do this, decide on a location for the data directory and copy it there if it isn't there already (a good choice would be to leave it in the `$GEOMROOT' directory in your SGI Geomview installation). Then edit the file `Geomview.app/CONFIG.gv' to change the setting of the variable `GEOMVIEW_DATA' to point to this directory (there are comments in the file telling you what to do). You can then remove the data directory from `Geomview.app'. To run geomview, double-click on `Geomview.app' from the workspace, or type `open Geomview.app' from the appropriate directory, or type `geomview' from a shell window. More Geomview documentation is in the `Geomview.app/doc' subdirectory. In particular, a copy of the manual is there. The `install' script puts copies of the files in `Geomview.app/bin/next' and `Geomview.app/man' into the directories you specified for executables and man pages, respectively. Once you have done the installation you can cut down one the disk space required by Geomview by removing all the files in these directories, since copies have been installed elsewhere. You should first test that your installed Geomview works properly because once you remove these files from their distribution directories you will not be able to do the installation again. File: geomview Node: NeXTStep Binary Detail, Prev: NeXT Binary Installation, Up: NeXT Binary Installation, Next: Source Code Installation Details of the NeXTStep Binary Installation ------------------------------------------- Other than the installation of the `Geomview.app' directory, the installation details of the NeXTStep binary distribution are the same as for the SGI distribution, *Note SGI Binary Detail::. Note that the directory referred to in the SGI distribution as `$GEOMROOT' is the `Geomview.app' directory in the NeXTStep distribution. File: geomview Node: Source Code Installation, Prev: NeXTStep Binary Detail, Up: Installation, Next: Obtaining Compiling and Installing the Source Code Distribution ===================================================== The main reason to get the source code distribution is to look at and/or work with the source code. If you are only concered with *using* Geomview it is better to get the binary distribution. It takes anywhere from 15 minutes to 1.5 hours to compile the entire source distribution, depending on what kind of computer you have. Let `$GEOMROOT' denote the full pathname of the Geomview source code directory; this is the directory called `Geomview' that is created when you unpack the distribution. This directory contains the Geomview source code as well as various other files and subdirectories that Geomview needs when it runs. Before doing any compilation you should edit the file `$GEOMROOT/makefiles/mk.site.default'. This file defines some `make' variables which specify your local configuration. This includes the pathnames of the directories into which Geomview will be installed, and possibly some other settings as well. There are comments in the file telling you what to do. This file is included by every Makefile in the source tree, so the settings you specify here are used throughout the source. If you will be compiling for both SGI and NeXT, you can do both in the same directory tree. By default the Makefiles are set up to put the objects files, libraries, and executables in directories which depend on the type of computer, so the two architectures will not interfere with each other. The Makefiles use a variable called `CPU' to determine the type of machine. Before doing any compilation you must arrange for this variable to have a value. There are two ways you can do this. 1. If you will always be compiling Geomview on the same type of computer (SGI or NeXT), edit the file `$GEOMROOT/makefiles/Makedefs.global' to set the `CPU' variable to either `iris4' or `NeXT'. The comments near the top of that file will tell you where to do this. 2. If you will be compiling on both types of computers you can set a shell environment variable named `CPU' to either `iris4' or `NeXT', and the Makefiles will inherit the value from the environment. The script `$GEOMROOT/config' determines which kind of computer you are on and sets this variable accordingly. To use this script, type `source config' in the (assuming a C-shell type shell) in the `$GEOMROOT' directory shell in which you plan to do the compilation. Or you can set the variable directly; it should be either `NeXT' or `iris4'. You will need to do this in every shell in which you plan to do compilation. Alternately, you could modify your shell initialization file (`.cshrc' or whatever) to set `CPU' appropriately. Note that many of the Makefiles refer to a variable called `MACHTYPE' to determine the type of machine. This is set to either `sgi' or `next', depending on the value of `CPU'. Once you have configured your source tree by editing the files as described above and setting the `CPU' variable, you can compile and install Geomview by typing `make install' in the `$GEOMROOT' directory. You can also type `make all', or equivalently just `make', to compile without installing, and then type `make install' later to install. You can use these same `make' comands in any subdirectory in the tree to recompile and/or install a part of Geomview or a module. If you want to compile fat binaries under NeXTStep 3.1, before doing any compilation edit the file `$GEOMROOT/makefiles/mk.next' to uncomment a particular line there. There are comments in the file telling you which line to uncomment. If you want to modify the complier flags used during compilation, edit the file `$GEOMROOT/makefiles/Makedefs.global'; the `COPTS' variable specifies the flags passed to the C compiler (cc). File: geomview Node: Obtaining, Prev: Source Code Installation, Up: Installation, Next: Function Index Obtaining Geomview ================== Geomview is available free via anonymous ftp from Internet host `geom.umn.edu', IP address 128.101.25.35. The Geomview distribution files are in the `pub/software/geomview' subdirectory. They are all tar archive files (`.tar' or `.tar.Z' files), so you should use binary mode in ftp for transferring them to your site. The main files are `geomview-sgi.tar.Z' The SGI binary distribution. Contains executables for running on any Silcon Graphics IRIS workstation, plus documentation and example files. `geomview-next.tar' The NeXTStep binary distribution. This contains fat binaries which will run on either a NeXT workstation running NeXTStep 3.0 or 3.1, or a 486 PC running NeXTStep 3.1. Also contains documentation and example files. This {.tar} file is not compressed because it contains the distribution compressed into a NeXT Installer package, and further compression actually increases the size of the file. To unpack `geomview-next.tar' on a NeXT, simple double-click on it in the Workspace. `geomview-src.tar.Z' The source code distribution; contains source code so you can compile Geomview and the distributed external modules on either an SGI or on a NeXT workstation running NeXTStep 3.0 or 3.1, or a 486 PC running NeXTStep 3.1. Also contains documentaion and examples files. Each of the above archive files contains the entire distribution: executables or source for Geomview itself, plus all distributed external modules, example data files, and documentation. These archive files are therefore rather large. If you do not have enough disk space on your workstation for the entire distribution, various pieces of the distribution are available separately in the `pub/software/geomview/pieces' subdirectory. See the file `README' in that directory for details. After retrieving any of the distribution archive files, you can unpack it with a command like the following % uncompress < geomview-sgi.tar.Z | tar xvopBf - This will unpack the contents of the archive file into a subdirectory named `Geomview'. Once unpacked, you can delete the archive file. The following is a sample ftp session for retreiving and unpacking the SGI binary distribution. After unpacking, see the file `README' for more information. artin% ftp geom.umn.edu Connected to geom.umn.edu. 220 cameron FTP server (Version 5.88 Thu Jun 25 16:41:41 CDT 1992) ready. Name (geom.umn.edu:mbp): anonymous 331 For password please enter your e-mail address or name and institution. Password:mbp@geom.umn.edu 230 Guest login ok, access restrictions apply. ftp> cd pub/software/geomview 250 CWD command successful. ftp> binary 200 Type set to I. ftp> get geomview-sgi.tar.Z 200 PORT command successful. 150 Opening BINARY mode data connection for geomview-sgi.tar.Z (5815980 bytes). 226 Transfer complete. local: geomview-sgi.tar.Z remote: geomview-sgi.tar.Z 5815980 bytes received in 28.67 seconds (1.98e+02 Kbytes/s) ftp> quit 221 Goodbye. artin% ls -l total 5680 -rw-rw-r-- 1 mbp 5815980 Aug 19 16:38 geomview-sgi.tar.Z artin% uncompress < geomview-sgi.tar.Z | tar xvopf - x ./CHANGES, 16910 bytes, 34 tape blocks ... artin% rm geomview-sgi.tar.Z File: geomview Node: Function Index, Prev: Obtaining, Up: Top Function Index ************** * Menu: * !: Gcl Reference. * <: Gcl Reference. * =: Gcl Reference. * >: Gcl Reference. * ?: Gcl Reference. * ??: Gcl Reference. * |: Gcl Reference. * all: Gcl Reference. * ap-override: Gcl Reference. * backcolor: Gcl Reference. * background-image: Gcl Reference. * bbox-color: Gcl Reference. * bbox-draw: Gcl Reference. * camera: Gcl Reference. * camera-draw: Gcl Reference. * camera-prop: Gcl Reference. * camera-reset: Gcl Reference. * car: Gcl Reference. * cdr: Gcl Reference. * clock: Gcl Reference. * command: Gcl Reference. * copy: Gcl Reference. * cursor-still: Gcl Reference. * cursor-twitch: Gcl Reference. * delete: Gcl Reference. * dice: Gcl Reference. * dimension: Gcl Reference. * dither: Gcl Reference. * draw: Gcl Reference. * echo: Gcl Reference. * emodule-clear: Gcl Reference. * emodule-define: Gcl Reference. * emodule-defined: Gcl Reference. * emodule-isrunning: Gcl Reference. * emodule-path: Gcl Reference. * emodule-run: Gcl Reference. * emodule-sort: Gcl Reference. * emodule-start: Gcl Reference. * emodule-transmit: Gcl Reference. * escale: Gcl Reference. * event-keys: Gcl Reference. * event-mode: Gcl Reference. * event-pick: Gcl Reference. * evert: Gcl Reference. * exit: Gcl Reference. * ezoom: Gcl Reference. * freeze: Gcl Reference. * geometry: Gcl Reference. * geomview-version: Gcl Reference. * hdefine: Gcl Reference. * help: Gcl Reference. * hmodel: Gcl Reference. * hsphere-draw: Gcl Reference. * if: Gcl Reference. * inhibit-warning: Gcl Reference. * input-translator: Gcl Reference. * interest: Gcl Reference. * lines-closer: Gcl Reference. * load: Gcl Reference. * load-path: Gcl Reference. * look: Gcl Reference. * look-encompass: Gcl Reference. * look-encompass-size: Gcl Reference. * look-recenter: Gcl Reference. * look-toward: Gcl Reference. * merge: Gcl Reference. * merge-ap: Gcl Reference. * merge-base-ap: Gcl Reference. * merge-baseap: Gcl Reference. * morehelp: Gcl Reference. * name-object: Gcl Reference. * ND-axes: Gcl Reference. * ND-color: Gcl Reference. * ND-xform: Gcl Reference. * ND-xform-get: Gcl Reference. * new-alien: Gcl Reference. * new-camera: Gcl Reference. * new-center: Gcl Reference. * new-geometry: Gcl Reference. * new-reset: Gcl Reference. * NeXT: Gcl Reference. * normalization: Gcl Reference. * pick: Gcl Reference. * pickable: Gcl Reference. * pick-invisible: Gcl Reference. * position: Gcl Reference. * position-at: Gcl Reference. * position-toward: Gcl Reference. * progn: Gcl Reference. * quit: Gcl Reference. * quote: Gcl Reference. * rawevent: Gcl Reference. * rawpick: Gcl Reference. * read: Gcl Reference. * real-id: Gcl Reference. * redraw: Gcl Reference. * regtable: Gcl Reference. * rehash-emodule-path: Gcl Reference. * replace-geometry: Gcl Reference. * rib-display: Gcl Reference. * rib-snapshot: Gcl Reference. * scale: Gcl Reference. * scene: Gcl Reference. * set-clock: Gcl Reference. * set-conformal-refine: Gcl Reference. * set-emodule-path: Gcl Reference. * setenv: Gcl Reference. * set-load-path: Gcl Reference. * set-motionscale: Gcl Reference. * sgi: Gcl Reference. * shell: Gcl Reference. * sleep-for: Gcl Reference. * sleep-until: Gcl Reference. * snapshot: Gcl Reference. * soft-shader: Gcl Reference. * space: Gcl Reference. * stereowin: Gcl Reference. * time-interests: Gcl Reference. * transform: Gcl Reference. * transform-incr: Gcl Reference. * transform-set: Gcl Reference. * ui-center: Gcl Reference. * ui-emotion-program: Gcl Reference. * ui-emotion-run: Gcl Reference. * ui-freeze: Gcl Reference. * ui-panel: Gcl Reference. * ui-target: Gcl Reference. * uninterest: Gcl Reference. * update: Gcl Reference. * update-draw: Gcl Reference. * window: Gcl Reference. * winenter: Gcl Reference. * write: Gcl Reference. * write-comments: Gcl Reference. * write-sexpr: Gcl Reference. * xform: Gcl Reference. * xform-incr: Gcl Reference. * xform-set: Gcl Reference. * zoom: Gcl Reference.